-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update update workflows #321
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change introduces new archives for GraalVM 17 and 20, that now include native-image
.
Before we can consider native-image
as part of GraalVM, like @dmikusa said, 11 must be monitored or... deprecated... since it seems to not be distributed "officially" anymore, see: https://www.graalvm.org/downloads/
This needs a little more work. I missed required changes to |
I think this is ready to go now. Need a quick re-review. Thanks |
1. Remove Java 11. This has gone end of life upstream, so it is being removed. 2. Remove Java 19. This has gone end of life upstream, so it is being removed. 3. Add Java 20. This is the new short-term release. 4. Update Java 17 to use the new Github release update dependency. We can now use this to fetch dependencies from upstream instead of the custom updater. This works for Java 17 and Java 20. Signed-off-by: Daniel Mikusa <dan@mikusa.com>
Signed-off-by: Daniel Mikusa <dan@mikusa.com>
The way the libjvm support works, it needs a tag called `native-image-svm` for the bundled JDK+native image. This commit adds those, even though they are duplicates. Signed-off-by: Daniel Mikusa <dan@mikusa.com>
Signed-off-by: Daniel Mikusa <dan@mikusa.com>
Summary
Use Cases
Fix updaters.
Resolves #327
Checklist